Optimized urgent scenario and emergency scenario mass/group messaging/notifications/communications service exposed/delivered via web user interface and mobile device application

ABSTRACT

Systems, methods, and devices for simultaneously distributing mass notifications to multiple users. A mass notification system receives input data and, based on this input data, creates notifications for mass distribution for urgent scenarios and emergency scenarios via Short Message Service (SMS) and/or Voice communication (audio recording or text to speech) The notifications are then transmitted to devices used by the users who are to be notified. The communication network control system confirms the indication of the emergency situation to the mobile device and notifies emergency personnel of the indication of the emergency situation. The communication network control system transmits an indication of the emergency situation to one or more additional mobile devices in the area. The message text and or voice recording is pre-configured/pre-set by the valid user. Target recipient groups for message/notification are also pre-configured/pre-set by the valid user.

FIELD OF THE INVENTION

The present invention relates to a method, apparatus, and system for mass notification and instruction to mobile devices. In the event of an urgent scenario/event or emergency scenario/event, time sensitivity and emotional duress present the need for an optimized technological capability for notifying applicable recipient groups, agencies, and entities for response/management/safety of persons.

In one embodiment of this invention, the user could be notified that their mobile device requires a software, firmware and/or hardware upgrade to implement the present invention. This upgrade could be conducted by the individual's own mobile device provider. This would now be one of many mobile devices connected to the disclosed network that would be alerted at the approximately exact time emergency to user is discovered within the predetermined geographical range of the individual emergency notification system.

BACKGROUND OF THE INVENTION

A notification system is a combination of software and hardware that provides a means of delivering messages to a set of recipients. For example, notification systems can send emails or text messages or make phone calls with automated messages. The complexity of the notification system is often dependent on the application. The use of notification systems range from simple publicity applications (e.g. sending notifications of a new product or a sale) to emergency applications (e.g. notifying individuals of a dangerous situation).

With the pervasive use and high availability of different types of computing devices (e.g. Personal Computer, laptop, terminal connected to a server, dumb terminal, tablet computer, PDA, Internet Protocol phone, smartphone), the notification system needs to be capable of reaching any type of computing device at any time and adapting the presentation of the notification to the capability of the computing device for the notification to have the broadest reach.

Existing notification systems establish connectivity with the devices to be notified at the time of sending a notification. When used as an emergency application, there is a need to keep constant connectivity with all the computing devices that need to receive notifications and to ensure the mobile device and application are running the correct version of the notification client where applicable.

Notification systems are generally unidirectional, whereby the notification is broadcasted or dispatched to a set of devices and there is little to no capability to extract information from the recipient of the notification. As such, there is a need for bi-directional capability in an emergency system, to extract information from the recipient of the notification and to manage the extracted information. For example, in an emergency notification application, it would be of value to request an acknowledgment that a user has received the notification and to maintain a record of which users have acknowledged the notification.

SUMMARY OF INVENTION

The present invention provides systems, methods, and application for simultaneously distributing emergency notifications to multiple users. The emergency notification system receives input data and, based on this input data, creates notifications for mass distribution. The notifications are then transmitted by the users who are to be notified. The message text and or voice recording is preconfigured/pre-set by the valid user. Target recipient groups for message/notification are also pre-configured/pre-set by the valid user.

The system includes a Software as a Service (SaaS) interface, a web user interface (web application, website) or a mobile device application “authentication.” “Authentication” is defined as valid/registered user ID and Password input, multi-digit PIN, or biometric authentication.

In a first aspect, the present invention provides a platform for sending notifications to a plurality of users, comprising:

-   -   A server locates mobile device and authenticate to device;     -   Next, the server opens mobile application for SAAS platform;     -   Furthermore, in an optional step, the server authenticates the         sending message as user validate and verify group/mass         communication/message/notification prior to distribution to         defined recipient groups and entities.     -   Next, the user clicks a button on the user's device to send         emergency notification;     -   Further action is validated and verified;     -   Message distribution is in progress and finds its end user;     -   Further, the server sends SMS and voice message to recipients;     -   SMS and Voice message can be sent to Law enforcing agencies and         Initiate/deploy urgent scenario or emergency scenario group/mass         communication/messaging. Audience/recipient group can include         emergency services (911, paramedics, federal agencies, state         agencies). Example: Click “button” in SaaS         application/website/web user interface/mobile application

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments are described with reference to the following figures, in which:

FIGS. 1A and 1B are schematic diagrams of a mass emergency notification system according to a non-limiting embodiment;

FIG. 2 is a block diagram of applications executable on an Emergency Work Flow of System (EWFS) of the system.

DETAILED DESCRIPTION OF THE DRAWINGS

The present invention will now be described with reference to FIGS. 1A, 1B and 2.

FIGS. 1A and 1B details two distinct workflows that are required for the invention “Optimized urgent scenario and emergency scenario mass/group messaging/notifications/communications service exposed/delivered via web user interface and mobile device application.” The proper sequence for these workflows are first “Emergency Notification System—Configuration” and second “Emergency Response Workflow.”

“Emergency Notification System—Configuration” (FIG. 1A)

Valid User (101): Valid user 101 represents a person or persons authorized by the manager, owner, operator, person in authority or persons in authority for a nonprofit organization, for profit organization, academic institution, small business, medium enterprise or large enterprise to administer and configure the emergency communications system.

Authenticate to Software as a Service (SaaS) platform (102): The valid user 101 uses a website browser (i.e. Google Chrome, Internet Explorer, Microsoft Edge, Apple Safari) to navigate to the website for this invention. The valid user 101 would “authenticate” or login to the account provisioned for organization using a valid identification (ID) and password.

Input Emergency message text (103): In the web form designated for pre-composing the emergency protocol message, the valid user 101 must input the emergency protocol message text. This emergency protocol message text is the text that would be distributed as a mobile text message to recipient mobile phone numbers and associated mobile devices in the event of product/service usage.

Select recipient groups for emergency message (104): In the web form designated for pre-selecting recipient mobile phone numbers and/or groups of numbers, the valid user 101 must select the determined recipient mobile phone numbers and/or groups of numbers that would receive the “emergency protocol message” in the event of product/service usage.

Logout (105): The valid user 101 exits the web form.

Access Mobile Application Store (106): The authorized user(s)/“Actor(s)” who operate within the organization use the mobile phone/device that is approved for product/service usage to access/open the mobile application store (i.e. Apple iOS App Store, Google Play Store).

Search, find and download application for SaaS platform (107): The authorized user(s)/“Actor(s)” input the mobile application name into the search feature for the mobile application store of the approved mobile phone/device.

Open application and authenticate (108): The authorized user(s)/“Actor(s)” open the installed application and complete the validation process and authentication process. The authorized user(s)/“Actor(s)” enables and configures biometric authentication (109).

Verify emergency message text (110): The authorized user(s)/“Actor(s)” view the application interface and verify “emergency protocol message” is successfully displayed.

Verify recipient groups (111): The authorized user(s)/“Actor(s)” view the application interface and verify recipient group names are successfully displayed.

Logout (112): Exit mobile application

“Emergency Response Workflow” (FIG. 1B)

FIG. 1B shows the workflow steps to be executed if/when an authorized user/“Actor” 151 for the product/service has identified an active threat/active shooter/eminent threat scenario.

Locate mobile device and authenticate to device (152): The authorized user/“Actor” 151 locates and takes hold of the approved mobile phone/device that has been configured for product/service usage.

Open mobile application for SaaS platform (153): The authorized user/“Actor” 151 locates mobile application associated with this product/service and open the mobile application.

Authenticate (154): The authorized user/“Actor” 151 inputs required data for application access.

Click button to send emergency notification (155): The authorized user/“Actor” 151 interacts with the application by clicking button designated for initiating/sending messaging.

Verify/validate action (156): The authorized user/“Actor” 151 completes validation step if validation is enabled/enforced.

Message distribution in-progress (157): SaaS platform will begin distributing text based notifications/messages to pre-selected mobile phone/device recipients and mobile phone/device recipient groups.

FIG. 2 illustrates the mobile application interface (201, 202) created for the product/service; integration with SaaS service servers (203) which are separate from the authorized user/“Actor” mobile phone/device; and illustrates text based message distribution to pre-selected mobile phone recipients and groups of mobile phone recipients (204). 

1.-2. (canceled)
 3. A method comprising: receiving, by a server, a first request to authenticate a first user at a first user device; authenticating the first user at the first user device and providing access to the first user at the first user device to a software as a service (SaaS) user interface displayed by the first user device; receiving, by the server, an emergency message text input in the SaaS user interface by the first user; receiving, by the server, a selection from the first user through the SaaS user interface of at least one group comprising a plurality of recipient devices to receive an emergency notification message comprising the emergency message text; receiving, by the server, a second request to authenticate a second user at a second user device; authenticating the second user at the second user device and providing access to the second user to the SaaS user interface displayed by the second user device; receiving, by the server from the second user device, a request to transmit the emergency notification message to the at least one group comprising the plurality of recipient devices; and transmitting the emergency notification message to each of the plurality of recipient devices.
 4. The method according to claim 3, further comprising: prior to authenticating the first user at the first user device, requesting authentication credentials of the first user; and receiving, by the server, the authentication credentials of the first user.
 5. The method according to claim 4, further comprising: prior to authenticating the second user at the second user device, requesting authentication credentials of the second user; and receiving the authentication credentials of the second user.
 6. The method according to claim 5, wherein the first user and the second user are different users having different authentication credentials.
 7. The method according to claim 5, wherein the authentication credentials of the first and second users comprise a user identification and a password.
 8. The method according to claim 5, wherein the authentication credentials of the second user comprise a fingerprint-based authentication credential.
 9. The method according to claim 3, further comprising: transmitting with the emergency notification message to each of the plurality of recipient devices, a request to confirm receipt of the emergency notification message.
 10. The method according to claim 3, wherein the emergency notification message sent to each of the plurality of recipient devices comprises an SMS and/or a voice message, each of the SMS and/or voice message comprising the emergency message text.
 11. The method according to claim 3, further comprising: prior to transmitting the emergency notification message to each of the plurality of recipient devices, requesting a verification from the second user that the emergency message text and the selected at least one group comprising the plurality of recipient devices to receive the emergency notification message are each accurate.
 12. A server comprising at least one processor and memory stored with instructions, which when executed by the at least one processor, cause the server to perform: receiving a first request to authenticate a first user at a first user device; authenticating the first user at the first user device and providing access to the first user at the first user device to a software as a service (SaaS) user interface displayed by the first user device; receiving an emergency message text input in the SaaS user interface by the first user; receiving a selection from the first user through the SaaS user interface of at least one group comprising a plurality of recipient devices to receive an emergency notification message comprising the emergency message text; receiving a second request to authenticate a second user at a second user device; authenticating the second user at the second user device and providing access to the second user to the SaaS user interface displayed by the second user device; receiving a request from the second user device to transmit the emergency notification message to the at least one group comprising the plurality of recipient devices; and transmitting the emergency notification message to each of the plurality of recipient devices.
 13. The server according to claim 12, wherein the memory is stored with further instructions, which when executed by the at least one processor, cause the server to perform: prior to authenticating the first user at the first user device, requesting authentication credentials of the first user; and receiving the authentication credentials of the first user.
 14. The server according to claim 13, wherein the memory is stored with further instructions, which when executed by the at least one processor, cause the server to perform: prior to authenticating the second user at the second user device, requesting authentication credentials of the second user; and receiving the authentication credentials of the second user.
 15. The server according to claim 14, wherein the first user and the second user are different users having different authentication credentials.
 16. The server according to claim 14, wherein the authentication credentials of the first and second users comprise a user identification and a password.
 17. The server according to claim 14, wherein the authentication credentials of the second user comprise a fingerprint-based authentication credential.
 18. The server according to claim 12, wherein the memory is stored with further instructions, which when executed by the at least one processor, cause the server to perform: transmitting with the emergency notification message to each of the plurality of recipient devices, a request to confirm receipt of the emergency notification message.
 19. The server according to claim 3, wherein the emergency notification message sent to each of the plurality of recipient devices comprises an SMS and/or a voice message, each of the SMS and/or voice message comprising the emergency message text.
 20. The server according to claim 12, wherein the memory is stored with further instructions, which when executed by the at least one processor, cause the server to perform: prior to transmitting the emergency notification message to each of the plurality of recipient devices, requesting a verification from the second user that the emergency message text and the selected at least one group comprising the plurality of recipient devices to receive the emergency notification message are each accurate.
 21. A system comprising: a server; a first user device associated with a first user; and a second user device associated with a second user; wherein the first user device comprises at least one processor and memory stored with instructions, which when executed by the at least one processor of the first user device, cause the first user device to perform: requesting authentication of the first user by the server to provide access to a software as a service (SaaS) user interface; displaying the SaaS user interface on a display of the first user device; and receiving an emergency message text input in the SaaS user interface by the first user and a selection from the first user through the SaaS user interface of at least one group comprising a plurality of recipient devices to receive an emergency notification message comprising the emergency message text; wherein the second user device comprises at least one processor and memory stored with instructions, which when executed by the at least one processor of the second user device, cause the second user device to perform: requesting authentication of the second user by the server to provide access to a the SaaS user interface; displaying the SaaS user interface on a display of the second user device; and receiving an input by the second user in the SaaS user interface requesting the server to transmit the emergency notification message to the at least one group comprising the plurality of recipient devices; and wherein the server comprises at least one processor and memory stored with instructions, which when executed by the at least one processor of the server, cause the server to perform: storing the emergency message text input and the selection of the at least one group comprising the plurality of recipient devices to receive the emergency notification message comprising the emergency message text; authenticating the second user at the second user device in response to the second user authentication request and enabling the second user to access the emergency message text input and the selection of the at least one group comprising the plurality of recipient devices input by the first user; and transmitting the emergency notification message to each of the plurality of recipient devices. 